home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000031_news@columbia.edu_Sat Jul 29 00:09:05 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
4KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA25523
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 29 Jul 1995 21:27:20 -0400
Received: by apakabar.cc.columbia.edu id AA21310
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 29 Jul 1995 21:27:18 -0400
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!panix!news.mathworks.com!uunet!in1.uu.net!omen!caf
From: caf@omen.com (Chuck Forsberg WA7KGX)
Subject: Re: Kermit download from CompuServe.. best setup??
Organization: Omen Technology INC
Date: Sat, 29 Jul 1995 00:09:05 GMT
Message-Id: <DCGB35.5vo@omen.com>
References: <3uidtu$r5c@hpber004.swiss.hp.com> <DC095G.Dp3@omen.com> <DCBqtq.G7q@omen.com> <1995Jul28.154724.57417@cc.usu.edu>
Lines: 58
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <1995Jul28.154724.57417@cc.usu.edu>,
Joe Doupnik <jrd@cc.usu.edu> wrote:
>In article <DCBqtq.G7q@omen.com>, caf@omen.com (Chuck Forsberg WA7KGX) writes:
>> In article <1995Jul23.093017.56880@cc.usu.edu>,
>> Joe Doupnik <jrd@cc.usu.edu> wrote:
>>> ...
>>> As Frank explained, the external protocol specification (the Kermit
>>>protocol) remains consistent over time and internal implementation stragegies
>>>remain internal. Enhancements to the Kermit protocol are backward compatible
>>>with the oldest Kermits.
>>
>> Apparently there are things about Kermit Frank does not
>> understand besides how to do valid benchmarks.
>
> Chuck: it's about time you stopped slamming people in public.
>It's disgusting, wastes bandwidth. Your posts continue to be destructive.
> Stop and reread my paragraph above more carefully.
> What you did, according to your paragraph below, was swipe
>code from C Kermit having that ancient Source stuff. You could have
>done what I did, implement the protocol fresh and cleanly. The spec is
>the same.
Talk about slamming people in public!
Doupnik's claim that I *SWIPED* (as in stole) code from C Kermit
is an unfounded, scurrilous libel on my honesty and business
ethics. I demand an immediate public retraction and apology.
The Kermit support in Professional-YAM and ZCOMM is based on the
SuperKermit "The Source" code which, in fact, I helped develop.
Despite Frank's attempted revision of historical fact, this code
was offered royalty-free to developers of general purpose comms
programs to entice them to add SuperKermit to their products.
> If you still have trouble implementing the Kermit protocol then
>we are happy to clarify details, but we don't write the code for
>other vendors.
> Joe D.
As Doupnik conveniently forgets, it was a problem with Columbia
Kermit, not Professional-YAM, that started this thread.
And, yes Joe, there was a change in the Kermit spec. The
original Kermit spec called for quoting of *all* control
characters. Professional-YAM customers were having problems
downloading from certain systems that were inserting control
characters into Kermit packets. So I modified the Kermit code
in Professional-YAM to ignore out of spec control characters
within Kermit packets, and the customers were able to use Kermit
in their environment. It shouldn't take a protocol wizard to
realize how Franks' recent changes to Kermit would break code
that was written to the older Kermit spec.
--
Chuck Forsberg WA7KGX caf@omen.COM 503-621-3406 FAX:-3735
Omen Technology Inc "The High Reliability Software"
Author of YMODEM, ZMODEM, Professional-YAM, ZCOMM, GSZ and DSZ
TeleGodzilla BBS: 503-621-3746 FTP: ftp.cs.pdx.edu pub/zmodem